Skip to content

fix(metrics): migrated from deprecated Node.js APIs to activeResources metric #2149

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
kirrg001 wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

fix(metrics): migrated from deprecated Node.js APIs to activeResources metric #2149

kirrg001 wants to merge 1 commit into from

Conversation

@kirrg001
Copy link
Contributor

@kirrg001 kirrg001 commented Nov 13, 2025 •
edited by aryamohanan
Loading

Changes:

Next Instana Release Date

23/02/2026

Release Plan – Phase 1

  • Create BE pull request (add activeResources metric) https://github.ibm.com/instana/backend/pull/35484
  • Merge the BE pull request. (The changes will be available in Pink)
  • Create UI client changes:
    • Remove activeHandles and activeRequests.
    • Use activeResources instead.
  • Raise UI pull request https://github.ibm.com/instana/ui-client/pull/24723
  • Test BE changes (pink) along with UI changes in the local environment.
  • Test tracer changes together with BE (pink) and UI client locally.
  • Merge UI pull request.
  • Release UI and BE.
  • Verify tracer changes with BE (production) and UI client (production).
  • Release Node.js tracer.

Release Plan – Phase 2

  • Remove activeHandles and activeRequests from BE.
  • Testing.

refs https://jsw.ibm.com/browse/INSTA-64143
refs https://jsw.ibm.com/browse/INSTA-64277

@kirrg001 kirrg001 added the v5 v5 release items label Nov 13, 2025
@kirrg001 kirrg001 mentioned this pull request Nov 13, 2025
Merged
23 tasks
@kirrg001 kirrg001 added merge later do not merge and removed v5 v5 release items labels Nov 14, 2025
@kirrg001
Copy link
Contributor Author

kirrg001 commented Nov 14, 2025

Migration path:

  • BE receives activeRequests + activeHandles OR activeResources and provides one single metric to the ui client
  • UI client dashboard metric only shows the activeResources
  • If both changes are live, we can merge this fix without a major release!

@kirrg001 kirrg001 changed the base branch from v5-release to main November 14, 2025 10:05
@kirrg001 kirrg001 changed the title fix(shared-metrics): merged activeHandles and activeRequests into activeResources Q1 2026: Merge activeHandles and activeRequests into activeResources Nov 14, 2025
@kirrg001 @aryamohanan
fix(shared-metrics): merged activeHandles and activeRequests into act…
038bec9 
…iveResources

refs https://jsw.ibm.com/browse/INSTA-64143

BREAKING CHANGE:
- https://nodejs.org/api/deprecations.html#dep0161-process_getactiverequests-and-process_getactivehandles
- We previously used the internal methods to get active requests and active handles
- These functions are officially deprecated and the official public fn getActiveResourcesInfo exposes the signals
  together.
- Its too much effort to determine which signal belongs to which category (request or handle).
- Decided to just return the full number of active resources
@aryamohanan aryamohanan self-assigned this Feb 9, 2026
@aryamohanan aryamohanan changed the title Q1 2026: Merge activeHandles and activeRequests into activeResources fix(metrics): migrated from deprecated Node.js APIs to activeResources metric Feb 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@aryamohanan aryamohanan

Labels

do not merge merge later

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@kirrg001 @aryamohanan